Configuration: What to Sequence
For information on how to create and order your initial configuration, see Initial Setup for Performance Rules. Here are Yottaa's recommendations on what to sequence:
Always include:
| Resource | Rule Type |
|---|---|
| All First Parties | Sequence Resource — load normally |
| iFrames | Sequence Resource — load normally |
| jQuery | Sequence Resource — load normally |
| All Third Parties |
Dynamic Sequencing — Spread Rule |
Include if Exists:
| Resource | Sequence Type | Examples |
|---|---|---|
| Platform CDN | Sequence Resource — load normally | Shopify CDN, Cloudfront CDN |
| Dynamic CMS | Sequence Resource — load normally | Adobe Scene7, Cloudinary |
| Analytics | Sequence Resource — load normally | Google Analytics, Adobe Ominutre |
|
Tag Managers |
Sequence Resource — load normally |
Google Tag Manager, UTag - Tealium |
| A/B Testing and Personalization | Sequence Resource — load normally | Optimizely, Monetate, etc. |
Optional:
You can use the Service Flow dashboard and the Performance Rules Workflow to determine whether to create rules for these resources.
| Resource | Sequence Type | Example |
|---|---|---|
| Application Performance Management (APM) and Real User Monitoring (RUM) | Sequence Resource — load normally | New Relic, Dynatrace, Soasta |
| Sequence Resource — delay until 2000 milliseconds after onload | ||
| Chat | Sequence Resource — delay until 5000 milliseconds after onload | Zendesk, Live Person, Live Chat Inch |